<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>nm-settings: NetworkManager Reference Manual</title>
<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="NetworkManager Reference Manual">
<link rel="up" href="manpages.html" title="Part I. Manual Pages">
<link rel="prev" href="nmtui.html" title="nmtui">
<link rel="next" href="nm-settings-keyfile.html" title="nm-settings-keyfile">
<meta name="generator" content="GTK-Doc V1.29 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle">
<td width="100%" align="left" class="shortcuts"></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
<td><a accesskey="u" href="manpages.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
<td><a accesskey="p" href="nmtui.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
<td><a accesskey="n" href="nm-settings-keyfile.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
</tr></table>
<div class="refentry">
<a name="nm-settings"></a><div class="titlepage"></div>
<div class="refnamediv"><table width="100%"><tr>
<td valign="top">
<h2><span class="refentrytitle">nm-settings</span></h2>
<p>nm-settings — Description of settings and properties of NetworkManager connection profiles</p>
</td>
<td class="gallery_image" valign="top" align="right"></td>
</tr></table></div>
<div class="refsect1">
<a name="description"></a><h2>Description</h2>
<p>
          NetworkManager is based on a concept of connection profiles, sometimes referred to as
          connections only. These connection profiles contain a network configuration. When
          NetworkManager activates a connection profile on a network device the configuration will
          be applied and an active network connection will be established. Users are free to create
          as many connection profiles as they see fit. Thus they are flexible in having various network
          configurations for different networking needs. The connection profiles are handled by
          NetworkManager via <span class="emphasis"><em>settings service</em></span> and are exported on D-Bus
          (<span class="emphasis"><em>/org/freedesktop/NetworkManager/Settings/&lt;num&gt;</em></span> objects).
          The conceptual objects can be described as follows:
          </p>
<div class="variablelist"><table border="0" class="variablelist">
<colgroup>
<col align="left" valign="top">
<col>
</colgroup>
<tbody><tr>
<td><p><span class="term">Connection (profile)</span></p></td>
<td><p>
                  A specific, encapsulated, independent group of settings describing
                  all the configuration required to connect to a specific network.
                  It is referred to by a unique identifier called the UUID. A connection
                  is tied to a one specific device type, but not necessarily a specific
                  hardware device. It is composed of one or more <span class="emphasis"><em>Settings</em></span>
                  objects.
                </p></td>
</tr></tbody>
</table></div>
<div class="variablelist"><table border="0" class="variablelist">
<colgroup>
<col align="left" valign="top">
<col>
</colgroup>
<tbody><tr>
<td><p><span class="term">Setting</span></p></td>
<td><p>
                  A group of related key/value pairs describing a specific piece of a
                  <span class="emphasis"><em>Connection (profile)</em></span>. Settings keys and allowed values are
                  described in the tables below. Keys are also referred to as properties.
                  Developers can find the setting objects and their properties in the libnm-core
                  sources. Look for the <code class="function">*_class_init</code> functions near the bottom
                  of each setting source file.
                </p></td>
</tr></tbody>
</table></div>
<div class="variablelist">
<p>
              The settings and properties shown in tables below list all available connection
              configuration options. However, note that not all settings are applicable to all
              connection types. NetworkManager provides a command-line tool <span class="emphasis"><em>nmcli</em></span>
              that allows direct configuration of the settings and properties according to a connection
              profile type. <span class="emphasis"><em>nmcli</em></span> connection editor has also a built-in
              <span class="emphasis"><em>describe</em></span> command that can display description of particular settings
              and properties of this page.
            </p>
<table border="0" class="variablelist">
<colgroup>
<col align="left" valign="top">
<col>
</colgroup>
<tbody></tbody>
</table>
</div>
<div class="refsect2">
<a name="id-1.2.7.4.3"></a><h3>connection setting</h3>
<p>General Connection Profile Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.connection.auth-retries"></a>auth-retries</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection. Currently this only applies to 802-1x authentication.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.autoconnect"></a>autoconnect</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.autoconnect-priority"></a>autoconnect-priority</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>The autoconnect priority. If the connection is set to autoconnect, connections with higher priority will be preferred. Defaults to 0. The higher number means higher priority.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.autoconnect-retries"></a>autoconnect-retries</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.autoconnect-slaves"></a>autoconnect-slaves</td>
<td align="left">NMSettingConnectionAutoconnectSlaves (int32)</td>
<td align="left"> </td>
<td>Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.gateway-ping-timeout"></a>gateway-ping-timeout</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.id"></a>id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.interface-name"></a>interface-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). For software devices this specifies the name of the created device. For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.lldp"></a>lldp</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Whether LLDP is enabled for the connection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.llmnr"></a>llmnr</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes"). This feature requires a plugin which supports LLMNR. Otherwise the setting has no effect. One such plugin is dns-systemd-resolved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.master"></a>master</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Interface name of the master device or UUID of the master connection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.mdns"></a>mdns</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Whether mDNS is enabled for the connection. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no"). This feature requires a plugin which supports mDNS. Otherwise the setting has no effect. One such plugin is dns-systemd-resolved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.metered"></a>metered</td>
<td align="left">NMMetered (int32)</td>
<td align="left"> </td>
<td>Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.multi-connect"></a>multi-connect</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.permissions"></a>permissions</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>An array of strings defining what access a given user has to this connection.  If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list.  When this is not empty, the connection can be active only when one of the specified users is logged into an active session.  Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed.  Any other values are ignored and reserved for future use.  [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use.  All of [type], [id], and [reserved] must be valid UTF-8.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.read-only"></a>read-only</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.secondaries"></a>secondaries</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>List of connection UUIDs that should be activated when the base connection itself is activated. Currently only VPN connections are supported.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.slave-type"></a>slave-type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.stable-id"></a>stable-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The '$' character is treated special to perform dynamic substitutions at runtime. Currently supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.timestamp"></a>timestamp</td>
<td align="left">uint64</td>
<td align="left">0</td>
<td>The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.type"></a>type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.uuid"></a>uuid</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A universally unique identifier for the connection, for example generated with libuuid.  It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network.  For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.wait-device-timeout"></a>wait-device-timeout</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. Note that this property only works together with NMSettingConnection:interface-name to identify the device that will be waited for. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.connection.zone"></a>zone</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The trust level of a the connection.  Free form case-insensitive string (for example "Home", "Work", "Public").  NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. When updating this property on a currently activated connection, the change takes effect immediately.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.4"></a><h3>6lowpan setting</h3>
<p>6LoWPAN Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings.property.6lowpan.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.5"></a><h3>802-1x setting</h3>
<p>IEEE 802.1x Authentication Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.altsubject-matches"></a>altsubject-matches</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.anonymous-identity"></a>anonymous-identity</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Anonymous identity string for EAP authentication methods.  Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.auth-timeout"></a>auth-timeout</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.ca-cert"></a>ca-cert</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the CA certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.ca-cert-password"></a>ca-cert-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.ca-cert-password-flags"></a>ca-cert-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "ca-cert-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.ca-path"></a>ca-path</td>
<td align="left">string</td>
<td align="left"> </td>
<td>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.client-cert"></a>client-cert</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the client certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.client-cert-password"></a>client-cert-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.client-cert-password-flags"></a>client-cert-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "client-cert-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.domain-suffix-match"></a>domain-suffix-match</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.eap"></a>eap</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>The allowed EAP method to be used when authenticating to the network with 802.1x.  Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast".  Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.identity"></a>identity</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Identity string for EAP authentication methods.  Often the user's user or login name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.optional"></a>optional</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.pac-file"></a>pac-file</td>
<td align="left">string</td>
<td align="left"> </td>
<td>UTF-8 encoded file path containing PAC for EAP-FAST.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.password"></a>password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.password-flags"></a>password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.password-raw"></a>password-raw</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.password-raw-flags"></a>password-raw-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password-raw" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase1-auth-flags"></a>phase1-auth-flags</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x settings. See the wpa_supplicant documentation for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase1-fast-provisioning"></a>phase1-fast-provisioning</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning).  See the wpa_supplicant documentation for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase1-peaplabel"></a>phase1-peaplabel</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Forces use of the new PEAP label during key derivation.  Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1.  Set to "1" to force use of the new PEAP label.  See the wpa_supplicant documentation for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase1-peapver"></a>phase1-peapver</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property.  When unset, the version reported by the server will be used.  Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version.  To do so, this property may be set to "0" or "1" to force that specific PEAP version.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-altsubject-matches"></a>phase2-altsubject-matches</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-auth"></a>phase2-auth</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Specifies the allowed "phase 2" inner non-EAP authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property.  Recognized non-EAP "phase 2" methods are "pap", "chap", "mschap", "mschapv2", "gtc", "otp", "md5", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-autheap"></a>phase2-autheap</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Specifies the allowed "phase 2" inner EAP-based authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property.  Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-ca-cert"></a>phase2-ca-cert</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-ca-cert-password"></a>phase2-ca-cert-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-ca-cert-password-flags"></a>phase2-ca-cert-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "phase2-ca-cert-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-ca-path"></a>phase2-ca-path</td>
<td align="left">string</td>
<td align="left"> </td>
<td>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-client-cert"></a>phase2-client-cert</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-client-cert-password"></a>phase2-client-cert-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-client-cert-password-flags"></a>phase2-client-cert-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "phase2-client-cert-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-domain-suffix-match"></a>phase2-domain-suffix-match</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication.  If a matching dNSName is found, this constraint is met.  If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-private-key"></a>phase2-private-key</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-private-key-password"></a>phase2-private-key-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-private-key-password-flags"></a>phase2-private-key-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "phase2-private-key-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.phase2-subject-match"></a>phase2-subject-match</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed.  This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.pin"></a>pin</td>
<td align="left">string</td>
<td align="left"> </td>
<td>PIN used for EAP authentication methods.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.pin-flags"></a>pin-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "pin" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.private-key"></a>private-key</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Contains the private key when the "eap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users.  Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.private-key-password"></a>private-key-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.private-key-password-flags"></a>private-key-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "private-key-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.subject-match"></a>subject-match</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed.  This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-1x.system-ca-certs"></a>system-ca-certs</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch.  The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.6"></a><h3>adsl setting</h3>
<p>ADSL Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.adsl.encapsulation"></a>encapsulation</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Encapsulation of ADSL connection.  Can be "vcmux" or "llc".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.adsl.password"></a>password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Password used to authenticate with the ADSL service.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.adsl.password-flags"></a>password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.adsl.protocol"></a>protocol</td>
<td align="left">string</td>
<td align="left"> </td>
<td>ADSL connection protocol.  Can be "pppoa", "pppoe" or "ipoatm".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.adsl.username"></a>username</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Username used to authenticate with the ADSL service.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.adsl.vci"></a>vci</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>VCI of ADSL connection</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.adsl.vpi"></a>vpi</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>VPI of ADSL connection</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.7"></a><h3>bluetooth setting</h3>
<p>Bluetooth Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.bluetooth.bdaddr"></a>bdaddr</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>The Bluetooth address of the device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bluetooth.type"></a>type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.8"></a><h3>bond setting</h3>
<p>Bonding Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.bond.interface-name"></a>interface-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Deprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the bond's interface name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bond.options"></a>options</td>
<td align="left">dict of string to string</td>
<td align="left">{'mode': 'balance-rr'}</td>
<td>Dictionary of key/value pairs of bonding options.  Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.9"></a><h3>bridge setting</h3>
<p>Bridging Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.ageing-time"></a>ageing-time</td>
<td align="left">uint32</td>
<td align="left">300</td>
<td>The Ethernet MAC address aging time, in seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.forward-delay"></a>forward-delay</td>
<td align="left">uint32</td>
<td align="left">15</td>
<td>The Spanning Tree Protocol (STP) forwarding delay, in seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.group-forward-mask"></a>group-forward-mask</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.hello-time"></a>hello-time</td>
<td align="left">uint32</td>
<td align="left">2</td>
<td>The Spanning Tree Protocol (STP) hello time, in seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.interface-name"></a>interface-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Deprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the bridge's interface name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.mac-address"></a>mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set. If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.max-age"></a>max-age</td>
<td align="left">uint32</td>
<td align="left">20</td>
<td>The Spanning Tree Protocol (STP) maximum message age, in seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.multicast-snooping"></a>multicast-snooping</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.priority"></a>priority</td>
<td align="left">uint32</td>
<td align="left">32768</td>
<td>Sets the Spanning Tree Protocol (STP) priority for this bridge.  Lower values are "better"; the lowest priority bridge will be elected the root bridge.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.stp"></a>stp</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.vlan-default-pvid"></a>vlan-default-pvid</td>
<td align="left">uint32</td>
<td align="left">1</td>
<td>The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.vlan-filtering"></a>vlan-filtering</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Control whether VLAN filtering is enabled on the bridge.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge.vlans"></a>vlans</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured  by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.10"></a><h3>bridge-port setting</h3>
<p>Bridge Port Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.bridge-port.hairpin-mode"></a>hairpin-mode</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge-port.path-cost"></a>path-cost</td>
<td align="left">uint32</td>
<td align="left">100</td>
<td>The Spanning Tree Protocol (STP) port cost for destinations via this port.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge-port.priority"></a>priority</td>
<td align="left">uint32</td>
<td align="left">32</td>
<td>The Spanning Tree Protocol (STP) priority of this bridge port.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.bridge-port.vlans"></a>vlans</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.11"></a><h3>cdma setting</h3>
<p>CDMA-based Mobile Broadband Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.cdma.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.cdma.number"></a>number</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The number to dial to establish the connection to the CDMA-based mobile broadband network, if any.  If not specified, the default number (#777) is used when required.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.cdma.password"></a>password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.cdma.password-flags"></a>password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.cdma.username"></a>username</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.12"></a><h3>dcb setting</h3>
<p>Data Center Bridging Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.app-fcoe-flags"></a>app-fcoe-flags</td>
<td align="left">NMSettingDcbFlags (uint32)</td>
<td align="left"> </td>
<td>Specifies the NMSettingDcbFlags for the DCB FCoE application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.app-fcoe-mode"></a>app-fcoe-mode</td>
<td align="left">string</td>
<td align="left">"fabric"</td>
<td>The FCoE controller mode; either "fabric" (default) or "vn2vn".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.app-fcoe-priority"></a>app-fcoe-priority</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority.  Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.app-fip-flags"></a>app-fip-flags</td>
<td align="left">NMSettingDcbFlags (uint32)</td>
<td align="left"> </td>
<td>Specifies the NMSettingDcbFlags for the DCB FIP application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.app-fip-priority"></a>app-fip-priority</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority.  Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.app-iscsi-flags"></a>app-iscsi-flags</td>
<td align="left">NMSettingDcbFlags (uint32)</td>
<td align="left"> </td>
<td>Specifies the NMSettingDcbFlags for the DCB iSCSI application.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.app-iscsi-priority"></a>app-iscsi-priority</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.priority-bandwidth"></a>priority-bandwidth</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use.  The sum of all percentages for priorities which belong to the same group must total 100 percents.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.priority-flow-control"></a>priority-flow-control</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.priority-flow-control-flags"></a>priority-flow-control-flags</td>
<td align="left">NMSettingDcbFlags (uint32)</td>
<td align="left"> </td>
<td>Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.priority-group-bandwidth"></a>priority-group-bandwidth</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group.  Allowed values are 0 - 100, and the sum of all values must total 100 percents.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.priority-group-flags"></a>priority-group-flags</td>
<td align="left">NMSettingDcbFlags (uint32)</td>
<td align="left"> </td>
<td>Specifies the NMSettingDcbFlags for DCB Priority Groups.  Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.priority-group-id"></a>priority-group-id</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID.  Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.priority-strict-bandwidth"></a>priority-strict-bandwidth</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.dcb.priority-traffic-class"></a>priority-traffic-class</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.13"></a><h3>dummy setting</h3>
<p>Dummy Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.14"></a><h3>ethtool setting</h3>
<p>Ethtool Ethernet Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.15"></a><h3>generic setting</h3>
<p>Generic Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.16"></a><h3>gsm setting</h3>
<p>GSM-based Mobile Broadband Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.apn"></a>apn</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network.  The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.auto-config"></a>auto-config</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.device-id"></a>device-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The device unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will only apply to the specified device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.home-only"></a>home-only</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.network-id"></a>network-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration.  If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.number"></a>number</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.password"></a>password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The password used to authenticate with the network, if required.  Many providers do not require a password, or accept any password.  But if a password is required, it is specified here.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.password-flags"></a>password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.pin"></a>pin</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If the SIM is locked with a PIN it must be unlocked before any other operations are requested.  Specify the PIN here to allow operation of the device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.pin-flags"></a>pin-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "pin" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.sim-id"></a>sim-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The SIM card unique identifier (as given by the WWAN management service) which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.sim-operator-id"></a>sim-operator-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to.  If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.gsm.username"></a>username</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The username used to authenticate with the network, if required.  Many providers do not require a username, or accept any username.  But if a username is required, it is specified here.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.17"></a><h3>infiniband setting</h3>
<p>Infiniband Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.infiniband.mac-address"></a>mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.infiniband.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.infiniband.p-key"></a>p-key</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0").  Otherwise it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.infiniband.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.infiniband.transport-mode"></a>transport-mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The IP-over-InfiniBand transport mode. Either "datagram" or "connected".</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.18"></a><h3>ipv4 setting</h3>
<p>IPv4 Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.address-data"></a>address-data</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of IPv4 addresses. Each address dictionary contains at least 'address' and 'prefix' entries, containing the IP address as a string, and the prefix length as a uint32. Additional attributes may also exist on some addresses.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.addresses"></a>addresses</td>
<td align="left">array of array of uint32</td>
<td align="left"> </td>
<td>Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'.  Array of IPv4 address structures.  Each IPv4 address structure is composed of 3 32-bit values; the first being the IPv4 address (network byte order), the second the prefix (1 - 32), and last the IPv4 gateway (network byte order). The gateway may be left as 0 if no gateway exists for that subnet.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dad-timeout"></a>dad-timeout</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail.  A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero).  A value greater than zero is a timeout in milliseconds. The property is currently implemented only for IPv4.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dhcp-client-id"></a>dhcp-client-id</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0. The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links. The special value "duid" generates a RFC4361-compliant client identifier based on a hash of the interface name as IAID and /etc/machine-id. The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key. If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dhcp-fqdn"></a>dhcp-fqdn</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dhcp-hostname"></a>dhcp-hostname</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dhcp-hostname-flags"></a>dhcp-hostname-flags</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Flags for the DHCP hostname and FQDN. Currently this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dhcp-iaid"></a>dhcp-iaid</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dhcp-send-hostname"></a>dhcp-send-hostname</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dhcp-timeout"></a>dhcp-timeout</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dns"></a>dns</td>
<td align="left">array of uint32</td>
<td align="left"> </td>
<td>Array of IP addresses of DNS servers (as network-byte-order integers)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dns-options"></a>dns-options</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dns-priority"></a>dns-priority</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>DNS servers priority. The relative priority for DNS servers specified by this setting.  A lower value is better (higher priority). Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile. When using dns=default, servers with higher priority will be on top of resolv.conf.  To prioritize a given server over another one within the same connection, just specify them in the desired order.  When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.  Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. When using a DNS resolver that supports Conditional Forwarding as dns=dnsmasq or dns=systemd-resolved, each connection is used to query domains in its search list.  Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually).  When multiple connections specify the same domain, the one with the highest priority (lowest numerical value) wins.  If a connection specifies a domain which is subdomain of another domain with a negative DNS priority value, the subdomain is ignored.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.dns-search"></a>dns-search</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Array of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.gateway"></a>gateway</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The gateway associated with this configuration. This is only meaningful if "addresses" is also set.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.ignore-auto-dns"></a>ignore-auto-dns</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When "method" is set to "auto" and this property to TRUE, automatically configured nameservers and search domains are ignored and only nameservers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.ignore-auto-routes"></a>ignore-auto-routes</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.may-fail"></a>may-fail</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out.  Note that at least one IP configuration must succeed or overall network configuration will still fail.  For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.method"></a>method</td>
<td align="left">string</td>
<td align="left"> </td>
<td>IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.never-default"></a>never-default</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.route-data"></a>route-data</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of IPv4 routes. Each route dictionary contains at least 'dest' and 'prefix' entries, containing the destination IP address as a string, and the prefix length as a uint32. Most routes will also have a 'gateway' entry, containing the gateway IP address as a string. If the route has a 'metric' entry (containing a uint32), that will be used as the metric for the route (otherwise NM will pick a default value appropriate to the device). Additional attributes may also exist on some routes.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.route-metric"></a>route-metric</td>
<td align="left">int64</td>
<td align="left">-1</td>
<td>The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.route-table"></a>route-table</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv4.routes"></a>routes</td>
<td align="left">array of array of uint32</td>
<td align="left"> </td>
<td>Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'.  Array of IPv4 route structures.  Each IPv4 route structure is composed of 4 32-bit values; the first being the destination IPv4 network or address (network byte order), the second the destination network or address prefix (1 - 32), the third being the next-hop (network byte order) if any, and the fourth being the route metric. If the metric is 0, NM will choose an appropriate default metric for the device. (There is no way to explicitly specify an actual metric of 0 with this property.)</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.19"></a><h3>ipv6 setting</h3>
<p>IPv6 Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.addr-gen-mode"></a>addr-gen-mode</td>
<td align="left">int32</td>
<td align="left">1</td>
<td>Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced. The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced. On D-Bus, the absence of an addr-gen-mode setting equals enabling stable-privacy. For keyfile plugin, the absence of the setting on disk means EUI64 so that the property doesn't change on upgrade from older versions. Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.address-data"></a>address-data</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of IPv6 addresses. Each address dictionary contains at least 'address' and 'prefix' entries, containing the IP address as a string, and the prefix length as a uint32. Additional attributes may also exist on some addresses.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.addresses"></a>addresses</td>
<td align="left">array of legacy IPv6 address struct (a(ayuay))</td>
<td align="left"> </td>
<td>Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'address-data' and 'gateway'.  Array of IPv6 address structures.  Each IPv6 address structure is composed of an IPv6 address, a prefix length (1 - 128), and an IPv6 gateway address. The gateway may be zeroed out if no gateway exists for that subnet.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dad-timeout"></a>dad-timeout</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network.  If an address conflict is detected, the activation will fail.  A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero).  A value greater than zero is a timeout in milliseconds. The property is currently implemented only for IPv4.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dhcp-duid"></a>dhcp-duid</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option. The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id. The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk. The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt"). When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dhcp-hostname"></a>dhcp-hostname</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dhcp-hostname-flags"></a>dhcp-hostname-flags</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Flags for the DHCP hostname and FQDN. Currently this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dhcp-iaid"></a>dhcp-iaid</td>
<td align="left">string</td>
<td align="left"> </td>
<td>A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dhcp-send-hostname"></a>dhcp-send-hostname</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer.  If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dhcp-timeout"></a>dhcp-timeout</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dns"></a>dns</td>
<td align="left">array of byte array</td>
<td align="left"> </td>
<td>Array of IP addresses of DNS servers (in network byte order)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dns-options"></a>dns-options</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dns-priority"></a>dns-priority</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>DNS servers priority. The relative priority for DNS servers specified by this setting.  A lower value is better (higher priority). Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections.  It does not disambiguate multiple DNS servers within the same connection profile. When using dns=default, servers with higher priority will be on top of resolv.conf.  To prioritize a given server over another one within the same connection, just specify them in the desired order.  When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.  Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. When using a DNS resolver that supports Conditional Forwarding as dns=dnsmasq or dns=systemd-resolved, each connection is used to query domains in its search list.  Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually).  When multiple connections specify the same domain, the one with the highest priority (lowest numerical value) wins.  If a connection specifies a domain which is subdomain of another domain with a negative DNS priority value, the subdomain is ignored.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.dns-search"></a>dns-search</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Array of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.gateway"></a>gateway</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The gateway associated with this configuration. This is only meaningful if "addresses" is also set.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.ignore-auto-dns"></a>ignore-auto-dns</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When "method" is set to "auto" and this property to TRUE, automatically configured nameservers and search domains are ignored and only nameservers and search domains specified in the "dns" and "dns-search" properties, if any, are used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.ignore-auto-routes"></a>ignore-auto-routes</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.ip6-privacy"></a>ip6-privacy</td>
<td align="left">NMSettingIP6ConfigPrivacy (int32)</td>
<td align="left"> </td>
<td>Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941.  If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64.  This enhances privacy, but could cause problems in some applications, on the other hand.  The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.may-fail"></a>may-fail</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out.  Note that at least one IP configuration must succeed or overall network configuration will still fail.  For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.method"></a>method</td>
<td align="left">string</td>
<td align="left"> </td>
<td>IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration.  The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.never-default"></a>never-default</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.ra-timeout"></a>ra-timeout</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device. Set to 2147483647 (MAXINT32) for infinity.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.route-data"></a>route-data</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of IPv6 routes. Each route dictionary contains at least 'dest' and 'prefix' entries, containing the destination IP address as a string, and the prefix length as a uint32. Most routes will also have a 'next-hop' entry, containing the next hop IP address as a string. If the route has a 'metric' entry (containing a uint32), that will be used as the metric for the route (otherwise NM will pick a default value appropriate to the device). Additional attributes may also exist on some routes.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.route-metric"></a>route-metric</td>
<td align="left">int64</td>
<td align="left">-1</td>
<td>The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.route-table"></a>route-table</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.routes"></a>routes</td>
<td align="left">array of legacy IPv6 route struct (a(ayuayu))</td>
<td align="left"> </td>
<td>Deprecated in favor of the 'route-data' property, but this can be used for backward-compatibility with older daemons. Note that if you send this property the daemon will ignore 'route-data'.  Array of IPv6 route structures.  Each IPv6 route structure is composed of an IPv6 address, a prefix length (1 - 128), an IPv6 next hop address (which may be zeroed out if there is no next hop), and a metric. If the metric is 0, NM will choose an appropriate default metric for the device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ipv6.token"></a>token</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Configure the token for draft-chown-6man-tokenised-ipv6-identifiers-02 IPv6 tokenized interface identifiers. Useful with eui64 addr-gen-mode.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.20"></a><h3>ip-tunnel setting</h3>
<p>IP Tunneling Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.encapsulation-limit"></a>encapsulation-limit</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>How many additional levels of encapsulation are permitted to be prepended to packets. This property applies only to IPv6 tunnels.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.flags"></a>flags</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Tunnel flags. Currently the following values are supported: NM_IP_TUNNEL_FLAG_IP6_IGN_ENCAP_LIMIT (0x1), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_TCLASS (0x2), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FLOWLABEL (0x4), NM_IP_TUNNEL_FLAG_IP6_MIP6_DEV (0x8), NM_IP_TUNNEL_FLAG_IP6_RCV_DSCP_COPY (0x10), NM_IP_TUNNEL_FLAG_IP6_USE_ORIG_FWMARK (0x20). They are valid only for IPv6 tunnels.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.flow-label"></a>flow-label</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The flow label to assign to tunnel packets. This property applies only to IPv6 tunnels.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.input-key"></a>input-key</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The key used for tunnel input packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.local"></a>local</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The local endpoint of the tunnel; the value can be empty, otherwise it must contain an IPv4 or IPv6 address.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.mode"></a>mode</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The tunneling mode, for example NM_IP_TUNNEL_MODE_IPIP (1) or NM_IP_TUNNEL_MODE_GRE (2).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.output-key"></a>output-key</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The key used for tunnel output packets; the property is valid only for certain tunnel modes (GRE, IP6GRE). If empty, no key is used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID the new device will be bound to so that tunneled packets will only be routed via that interface.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.path-mtu-discovery"></a>path-mtu-discovery</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Whether to enable Path MTU Discovery on this tunnel.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.remote"></a>remote</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The remote endpoint of the tunnel; the value must contain an IPv4 or IPv6 address.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.tos"></a>tos</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The type of service (IPv4) or traffic class (IPv6) field to be set on tunneled packets.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ip-tunnel.ttl"></a>ttl</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The TTL to assign to tunneled packets. 0 is a special value meaning that packets inherit the TTL value.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.21"></a><h3>macsec setting</h3>
<p>MACSec Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.macsec.encrypt"></a>encrypt</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Whether the transmitted traffic must be encrypted.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macsec.mka-cak"></a>mka-cak</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The pre-shared CAK (Connectivity Association Key) for MACsec Key Agreement.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macsec.mka-cak-flags"></a>mka-cak-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "mka-cak" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macsec.mka-ckn"></a>mka-ckn</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The pre-shared CKN (Connectivity-association Key Name) for MACsec Key Agreement.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macsec.mode"></a>mode</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Specifies how the CAK (Connectivity Association Key) for MKA (MACsec Key Agreement) is obtained.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macsec.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID from which this MACSEC interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macsec.port"></a>port</td>
<td align="left">int32</td>
<td align="left">1</td>
<td>The port component of the SCI (Secure Channel Identifier), between 1 and 65534.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macsec.send-sci"></a>send-sci</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Specifies whether the SCI (Secure Channel Identifier) is included in every packet.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macsec.validation"></a>validation</td>
<td align="left">int32</td>
<td align="left">2</td>
<td>Specifies the validation mode for incoming frames.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.22"></a><h3>macvlan setting</h3>
<p>MAC VLAN Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.macvlan.mode"></a>mode</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The macvlan mode, which specifies the communication mechanism between multiple macvlans on the same lower device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macvlan.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID from which this MAC-VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macvlan.promiscuous"></a>promiscuous</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Whether the interface should be put in promiscuous mode.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.macvlan.tap"></a>tap</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Whether the interface should be a MACVTAP.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.23"></a><h3>match setting</h3>
<p>Match settings..</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings.property.match.interface-name"></a>interface-name</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of interface names to match. Each element is a shell wildcard pattern.  When an element is prefixed with exclamation mark (!) the condition is inverted. A candidate interface name is considered matching when both these conditions are satisfied: (a) any of the elements not prefixed with '!' matches or there aren't such elements; (b) none of the elements prefixed with '!' match.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.24"></a><h3>802-11-olpc-mesh setting</h3>
<p>OLPC Wireless Mesh Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-olpc-mesh.channel"></a>channel</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Channel on which the mesh network to join is located.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-olpc-mesh.dhcp-anycast-address"></a>dhcp-anycast-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>Anycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the request.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-olpc-mesh.ssid"></a>ssid</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>SSID of the mesh network to join.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.25"></a><h3>ovs-bridge setting</h3>
<p>OvsBridge Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-bridge.datapath-type"></a>datapath-type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The data path type. One of "system", "netdev" or empty.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-bridge.fail-mode"></a>fail-mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The bridge failure mode. One of "secure", "standalone" or empty.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-bridge.mcast-snooping-enable"></a>mcast-snooping-enable</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Enable or disable multicast snooping.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-bridge.rstp-enable"></a>rstp-enable</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Enable or disable RSTP.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-bridge.stp-enable"></a>stp-enable</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Enable or disable STP.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.26"></a><h3>ovs-dpdk setting</h3>
<p>OvsDpdk Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings.property.ovs-dpdk.devargs"></a>devargs</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Open vSwitch DPDK device arguments.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.27"></a><h3>ovs-interface setting</h3>
<p>Open vSwitch Interface Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings.property.ovs-interface.type"></a>type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The interface type. Either "internal", "system", "patch", "dpdk", or empty.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.28"></a><h3>ovs-patch setting</h3>
<p>OvsPatch Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings.property.ovs-patch.peer"></a>peer</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Specifies the unicast destination IP address of a remote Open vSwitch bridge port to connect to.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.29"></a><h3>ovs-port setting</h3>
<p>OvsPort Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-port.bond-downdelay"></a>bond-downdelay</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The time port must be inactive in order to be considered down.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-port.bond-mode"></a>bond-mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Bonding mode. One of "active-backup", "balance-slb", or "balance-tcp".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-port.bond-updelay"></a>bond-updelay</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The time port must be active before it starts forwarding traffic.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-port.lacp"></a>lacp</td>
<td align="left">string</td>
<td align="left"> </td>
<td>LACP mode. One of "active", "off", or "passive".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-port.tag"></a>tag</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The VLAN tag in the range 0-4095.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ovs-port.vlan-mode"></a>vlan-mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The VLAN mode. One of "access", "native-tagged", "native-untagged", "trunk" or unset.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.30"></a><h3>ppp setting</h3>
<p>Point-to-Point Protocol Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.baud"></a>baud</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, instruct pppd to set the serial port to the specified baudrate.  This value should normally be left as 0 to automatically choose the speed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.crtscts"></a>crtscts</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, specify that pppd should set the serial port to use hardware flow control with RTS and CTS signals.  This value should normally be set to FALSE.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.lcp-echo-failure"></a>lcp-echo-failure</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, instruct pppd to presume the connection to the peer has failed if the specified number of LCP echo-requests go unanswered by the peer.  The "lcp-echo-interval" property must also be set to a non-zero value if this property is used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.lcp-echo-interval"></a>lcp-echo-interval</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, instruct pppd to send an LCP echo-request frame to the peer every n seconds (where n is the specified value).  Note that some PPP peers will respond to echo requests and some will not, and it is not possible to autodetect this.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.mppe-stateful"></a>mppe-stateful</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, stateful MPPE is used.  See pppd documentation for more information on stateful MPPE.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.mru"></a>mru</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, instruct pppd to request that the peer send packets no larger than the specified size.  If non-zero, the MRU should be between 128 and 16384.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, instruct pppd to send packets no larger than the specified size.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.no-vj-comp"></a>no-vj-comp</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, Van Jacobsen TCP header compression will not be requested.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.noauth"></a>noauth</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>If TRUE, do not require the other side (usually the PPP server) to authenticate itself to the client.  If FALSE, require authentication from the remote side.  In almost all cases, this should be TRUE.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.nobsdcomp"></a>nobsdcomp</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, BSD compression will not be requested.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.nodeflate"></a>nodeflate</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, "deflate" compression will not be requested.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.refuse-chap"></a>refuse-chap</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, the CHAP authentication method will not be used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.refuse-eap"></a>refuse-eap</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, the EAP authentication method will not be used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.refuse-mschap"></a>refuse-mschap</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, the MSCHAP authentication method will not be used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.refuse-mschapv2"></a>refuse-mschapv2</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, the MSCHAPv2 authentication method will not be used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.refuse-pap"></a>refuse-pap</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, the PAP authentication method will not be used.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.require-mppe"></a>require-mppe</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session.  If either 64-bit or 128-bit MPPE is not available the session will fail.  Note that MPPE is not used on mobile broadband connections.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.ppp.require-mppe-128"></a>require-mppe-128</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, 128-bit MPPE (Microsoft Point-to-Point Encryption) will be required for the PPP session, and the "require-mppe" property must also be set to TRUE.  If 128-bit MPPE is not available the session will fail.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.31"></a><h3>pppoe setting</h3>
<p>PPP-over-Ethernet Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.pppoe.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name on which this PPPoE connection should be created.  If this property is not specified, the connection is activated on the interface specified in "interface-name" of NMSettingConnection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.pppoe.password"></a>password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Password used to authenticate with the PPPoE service.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.pppoe.password-flags"></a>password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.pppoe.service"></a>service</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If specified, instruct PPPoE to only initiate sessions with access concentrators that provide the specified service.  For most providers, this should be left blank.  It is only required if there are multiple access concentrators or a specific service is known to be required.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.pppoe.username"></a>username</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Username used to authenticate with the PPPoE service.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.32"></a><h3>proxy setting</h3>
<p>WWW Proxy Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.proxy.browser-only"></a>browser-only</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Whether the proxy configuration is for browser only.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.proxy.method"></a>method</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Method for proxy configuration, Default is NM_SETTING_PROXY_METHOD_NONE (0)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.proxy.pac-script"></a>pac-script</td>
<td align="left">string</td>
<td align="left"> </td>
<td>PAC script for the connection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.proxy.pac-url"></a>pac-url</td>
<td align="left">string</td>
<td align="left"> </td>
<td>PAC URL for obtaining PAC file.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.33"></a><h3>serial setting</h3>
<p>Serial Link Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.serial.baud"></a>baud</td>
<td align="left">uint32</td>
<td align="left">57600</td>
<td>Speed to use for communication over the serial port.  Note that this value usually has no effect for mobile broadband modems as they generally ignore speed settings and use the highest available speed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.serial.bits"></a>bits</td>
<td align="left">uint32</td>
<td align="left">8</td>
<td>Byte-width of the serial communication. The 8 in "8n1" for example.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.serial.parity"></a>parity</td>
<td align="left">byte</td>
<td align="left"> </td>
<td>The connection parity: 69 (ASCII 'E') for even parity, 111 (ASCII 'o') for odd, 110 (ASCII 'n') for none.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.serial.send-delay"></a>send-delay</td>
<td align="left">uint64</td>
<td align="left">0</td>
<td>Time to delay between each byte sent to the modem, in microseconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.serial.stopbits"></a>stopbits</td>
<td align="left">uint32</td>
<td align="left">1</td>
<td>Number of stop bits for communication on the serial port.  Either 1 or 2. The 1 in "8n1" for example.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.34"></a><h3>sriov setting</h3>
<p>SR-IOV settings..</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.sriov.autoprobe-drivers"></a>autoprobe-drivers</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>Whether to autoprobe virtual functions by a compatible driver. If set to NM_TERNARY_TRUE (1), the kernel will try to bind VFs to a compatible driver and if this succeeds a new network interface will be instantiated for each VF. If set to NM_TERNARY_FALSE (0), VFs will not be claimed and no network interfaces will be created for them. When set to NM_TERNARY_DEFAULT (-1), the global default is used; in case the global default is unspecified it is assumed to be NM_TERNARY_TRUE (1).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.sriov.total-vfs"></a>total-vfs</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The total number of virtual functions to create. Note that when the sriov setting is present NetworkManager enforces the number of virtual functions on the interface also when it is zero. To prevent any changes to SR-IOV parameters don't add a sriov setting to the connection.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.sriov.vfs"></a>vfs</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of virtual function descriptors. Each VF descriptor is a dictionary mapping attribute names to GVariant values. The 'index' entry is mandatory for each VF. When represented as string a VF is in the form: "INDEX [ATTR=VALUE[ ATTR=VALUE]...]". for example: "2 mac=00:11:22:33:44:55 spoof-check=true". Multiple VFs can be specified using a comma as separator. Currently the following attributes are supported: mac, spoof-check, trust, min-tx-rate, max-tx-rate, vlans. The "vlans" attribute is represented as a semicolon-separated list of VLAN descriptors, where each descriptor has the form "ID[.PRIORITY[.PROTO]]". PROTO can be either 'q' for 802.1Q (the default) or 'ad' for 802.1ad.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.35"></a><h3>tc setting</h3>
<p>Linux Traffic Control Settings..</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.tc.qdiscs"></a>qdiscs</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of TC queueing disciplines.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.tc.tfilters"></a>tfilters</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Array of TC traffic filters.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.36"></a><h3>team setting</h3>
<p>Teaming Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.team.config"></a>config</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The JSON configuration for the team network interface.  The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used.  See man teamd.conf for the format details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.interface-name"></a>interface-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Deprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the team's interface name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.link-watchers"></a>link-watchers</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are:   ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.mcast-rejoin-count"></a>mcast-rejoin-count</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd mcast_rejoin.count.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.mcast-rejoin-interval"></a>mcast-rejoin-interval</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd mcast_rejoin.interval.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.notify-peers-count"></a>notify-peers-count</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd notify_peers.count.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.notify-peers-interval"></a>notify-peers-interval</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd notify_peers.interval.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.runner"></a>runner</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Corresponds to the teamd runner.name. Permitted values are: "roundrobin", "broadcast", "activebackup", "loadbalance", "lacp", "random".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.runner-active"></a>runner-active</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Corresponds to the teamd runner.active.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.runner-agg-select-policy"></a>runner-agg-select-policy</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Corresponds to the teamd runner.agg_select_policy.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.runner-fast-rate"></a>runner-fast-rate</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Corresponds to the teamd runner.fast_rate.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.runner-hwaddr-policy"></a>runner-hwaddr-policy</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Corresponds to the teamd runner.hwaddr_policy.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.runner-min-ports"></a>runner-min-ports</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd runner.min_ports.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.runner-sys-prio"></a>runner-sys-prio</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd runner.sys_prio.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.runner-tx-balancer"></a>runner-tx-balancer</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Corresponds to the teamd runner.tx_balancer.name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.runner-tx-balancer-interval"></a>runner-tx-balancer-interval</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd runner.tx_balancer.interval.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team.runner-tx-hash"></a>runner-tx-hash</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Corresponds to the teamd runner.tx_hash.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.37"></a><h3>team-port setting</h3>
<p>Team Port Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.team-port.config"></a>config</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The JSON configuration for the team port. The property should contain raw JSON configuration data suitable for teamd, because the value is passed directly to teamd. If not specified, the default configuration is used. See man teamd.conf for the format details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team-port.lacp-key"></a>lacp-key</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd ports.PORTIFNAME.lacp_key.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team-port.lacp-prio"></a>lacp-prio</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd ports.PORTIFNAME.lacp_prio.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team-port.link-watchers"></a>link-watchers</td>
<td align="left">array of vardict</td>
<td align="left"> </td>
<td>Link watchers configuration for the connection: each link watcher is defined by a dictionary, whose keys depend upon the selected link watcher. Available link watchers are 'ethtool', 'nsna_ping' and 'arp_ping' and it is specified in the dictionary with the key 'name'. Available keys are:   ethtool: 'delay-up', 'delay-down', 'init-wait'; nsna_ping: 'init-wait', 'interval', 'missed-max', 'target-host'; arp_ping: all the ones in nsna_ping and 'source-host', 'validate-active', 'validate-inactive', 'send-always'. See teamd.conf man for more details.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team-port.prio"></a>prio</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Corresponds to the teamd ports.PORTIFNAME.prio.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team-port.queue-id"></a>queue-id</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>Corresponds to the teamd ports.PORTIFNAME.queue_id. When set to -1 means the parameter is skipped from the json config.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.team-port.sticky"></a>sticky</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Corresponds to the teamd ports.PORTIFNAME.sticky.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.38"></a><h3>tun setting</h3>
<p>Tunnel Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.tun.group"></a>group</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The group ID which will own the device. If set to NULL everyone will be able to use the device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.tun.mode"></a>mode</td>
<td align="left">uint32</td>
<td align="left">1</td>
<td>The operating mode of the virtual device. Allowed values are NM_SETTING_TUN_MODE_TUN (1) to create a layer 3 device and NM_SETTING_TUN_MODE_TAP (2) to create an Ethernet-like layer 2 one.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.tun.multi-queue"></a>multi-queue</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If the property is set to TRUE, the interface will support multiple file descriptors (queues) to parallelize packet sending or receiving. Otherwise, the interface will only support a single queue.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.tun.owner"></a>owner</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The user ID which will own the device. If set to NULL everyone will be able to use the device.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.tun.pi"></a>pi</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE the interface will prepend a 4 byte header describing the physical interface to the packets.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.tun.vnet-hdr"></a>vnet-hdr</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE the IFF_VNET_HDR the tunnel packets will include a virtio network header.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.39"></a><h3>user setting</h3>
<p>General User Profile Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody><tr>
<td align="left">
<a name="nm-settings.property.user.data"></a>data</td>
<td align="left">dict of string to string</td>
<td align="left">{}</td>
<td>A dictionary of key/value pairs with user data. This data is ignored by NetworkManager and can be used at the users discretion. The keys only support a strict ascii format, but the values can be arbitrary UTF8 strings up to a certain length.</td>
</tr></tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.40"></a><h3>vlan setting</h3>
<p>VLAN Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.vlan.egress-priority-map"></a>egress-priority-map</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>For outgoing packets, a list of mappings from Linux SKB priorities to 802.1p priorities.  The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vlan.flags"></a>flags</td>
<td align="left">NMVlanFlags (uint32)</td>
<td align="left"> </td>
<td>One or more flags which control the behavior and features of the VLAN interface.  Flags include NM_VLAN_FLAG_REORDER_HEADERS (0x1) (reordering of output packet headers), NM_VLAN_FLAG_GVRP (0x2) (use of the GVRP protocol), and NM_VLAN_FLAG_LOOSE_BINDING (0x4) (loose binding of the interface to its master device's operating state). NM_VLAN_FLAG_MVRP (0x8) (use of the MVRP protocol). The default value of this property is NM_VLAN_FLAG_REORDER_HEADERS, but it used to be 0. To preserve backward compatibility, the default-value in the D-Bus API continues to be 0 and a missing property on D-Bus is still considered as 0.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vlan.id"></a>id</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The VLAN identifier that the interface created by this connection should be assigned. The valid range is from 0 to 4094, without the reserved id 4095.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vlan.ingress-priority-map"></a>ingress-priority-map</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>For incoming packets, a list of mappings from 802.1p priorities to Linux SKB priorities.  The mapping is given in the format "from:to" where both "from" and "to" are unsigned integers, ie "7:3".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vlan.interface-name"></a>interface-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Deprecated in favor of connection.interface-name, but can be used for backward-compatibility with older daemons, to set the vlan's interface name.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vlan.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID from which this VLAN interface should be created.  If this property is not specified, the connection must contain an "802-3-ethernet" setting with a "mac-address" property.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.41"></a><h3>vpn setting</h3>
<p>VPN Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.vpn.data"></a>data</td>
<td align="left">dict of string to string</td>
<td align="left">{}</td>
<td>Dictionary of key/value pairs of VPN plugin specific data.  Both keys and values must be strings.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vpn.persistent"></a>persistent</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If the VPN service supports persistence, and this property is TRUE, the VPN will attempt to stay connected across link changes and outages, until explicitly disconnected.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vpn.secrets"></a>secrets</td>
<td align="left">dict of string to string</td>
<td align="left">{}</td>
<td>Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys.  Both keys and values must be strings.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vpn.service-type"></a>service-type</td>
<td align="left">string</td>
<td align="left"> </td>
<td>D-Bus service name of the VPN plugin that this setting uses to connect to its network.  i.e. org.freedesktop.NetworkManager.vpnc for the vpnc plugin.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vpn.timeout"></a>timeout</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Timeout for the VPN service to establish the connection. Some services may take quite a long time to connect. Value of 0 means a default timeout, which is 60 seconds (unless overridden by vpn.timeout in configuration file). Values greater than zero mean timeout in seconds.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vpn.user-name"></a>user-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If the VPN connection requires a user name for authentication, that name should be provided here.  If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty.  If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.42"></a><h3>vxlan setting</h3>
<p>VXLAN Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.ageing"></a>ageing</td>
<td align="left">uint32</td>
<td align="left">300</td>
<td>Specifies the lifetime in seconds of FDB entries learnt by the kernel.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.destination-port"></a>destination-port</td>
<td align="left">uint32</td>
<td align="left">8472</td>
<td>Specifies the UDP destination port to communicate to the remote VXLAN tunnel endpoint.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.id"></a>id</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.l2-miss"></a>l2-miss</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Specifies whether netlink LL ADDR miss notifications are generated.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.l3-miss"></a>l3-miss</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Specifies whether netlink IP ADDR miss notifications are generated.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.learning"></a>learning</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Specifies whether unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.limit"></a>limit</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the maximum number of FDB entries. A value of zero means that the kernel will store unlimited entries.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.local"></a>local</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the source IP address to use in outgoing packets.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.parent"></a>parent</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If given, specifies the parent interface name or parent connection UUID.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.proxy"></a>proxy</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Specifies whether ARP proxy is turned on.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.remote"></a>remote</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database, or the multicast IP address to join.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.rsc"></a>rsc</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>Specifies whether route short circuit is turned on.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.source-port-max"></a>source-port-max</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the maximum UDP source port to communicate to the remote VXLAN tunnel endpoint.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.source-port-min"></a>source-port-min</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the minimum UDP source port to communicate to the remote VXLAN tunnel endpoint.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.tos"></a>tos</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the TOS value to use in outgoing packets.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.vxlan.ttl"></a>ttl</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Specifies the time-to-live value to use in outgoing packets.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.43"></a><h3>wifi-p2p setting</h3>
<p>Wi-Fi P2P Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.wifi-p2p.peer"></a>peer</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The P2P device that should be connected to. Currently this is the only way to create or join a group.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wifi-p2p.wfd-ies"></a>wfd-ies</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>The Wi-Fi Display (WFD) Information Elements (IEs) to set. Wi-Fi Display requires a protocol specific information element to be set in certain Wi-Fi frames. These can be specified here for the purpose of establishing a connection. This setting is only useful when implementing a Wi-Fi Display client.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wifi-p2p.wps-method"></a>wps-method</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Flags indicating which mode of WPS is to be used. There's little point in changing the default setting as NetworkManager will automatically determine the best method to use.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.44"></a><h3>wimax setting</h3>
<p>WiMax Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.wimax.mac-address"></a>mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, this connection will only apply to the WiMAX device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing). Deprecated: 1</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wimax.network-name"></a>network-name</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Network Service Provider (NSP) name of the WiMAX network this connection should use. Deprecated: 1</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.45"></a><h3>802-3-ethernet setting</h3>
<p>Wired Ethernet Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.assigned-mac-address"></a>assigned-mac-address</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.auto-negotiate"></a>auto-negotiate</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>When TRUE, enforce auto-negotiation of speed and duplex mode. If "speed" and "duplex" properties are both specified, only that single mode will be advertised and accepted during the link auto-negotiation process: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. When FALSE, "speed" and "duplex" properties should be both set or link configuration will be skipped.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.cloned-mac-address"></a>cloned-mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>This D-Bus field is deprecated in favor of "assigned-mac-address" which is more flexible and allows specifying special variants like "random". For libnm and nmcli, this field is called "cloned-mac-address".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.duplex"></a>duplex</td>
<td align="left">string</td>
<td align="left"> </td>
<td>When a value is set, either "half" or "full", configures the device to use the specified duplex mode. If "auto-negotiate" is "yes" the specified duplex mode will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabits modes, as in these cases link negotiation is mandatory. If the value is unset (the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported duplex modes. Must be set together with the "speed" property if specified. Before specifying a duplex mode be sure your device supports it.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.generate-mac-address-mask"></a>generate-mac-address-mask</td>
<td align="left">string</td>
<td align="left"> </td>
<td>With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address. If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address. If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm. If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address. If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.mac-address"></a>mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, this connection will only apply to the Ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.mac-address-blacklist"></a>mac-address-blacklist</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>If specified, this connection will never apply to the Ethernet device whose permanent MAC address matches an address in the list.  Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.port"></a>port</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Specific port type to use if the device supports multiple attachment methods.  One of "tp" (Twisted Pair), "aui" (Attachment Unit Interface), "bnc" (Thin Ethernet) or "mii" (Media Independent Interface). If the device supports only one port type, this setting is ignored.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.s390-nettype"></a>s390-nettype</td>
<td align="left">string</td>
<td align="left"> </td>
<td>s390 network device type; one of "qeth", "lcs", or "ctc", representing the different types of virtual network devices available on s390 systems.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.s390-options"></a>s390-options</td>
<td align="left">dict of string to string</td>
<td align="left">{}</td>
<td>Dictionary of key/value pairs of s390-specific device options.  Both keys and values must be strings.  Allowed keys include "portno", "layer2", "portname", "protocol", among others.  Key names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.s390-subchannels"></a>s390-subchannels</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>Identifies specific subchannels that this network device uses for communication with z/VM or s390 host.  Like the "mac-address" property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels.  The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.speed"></a>speed</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>When a value greater than 0 is set, configures the device to use the specified speed. If "auto-negotiate" is "yes" the specified speed will be the only one advertised during link negotiation: this works only for BASE-T 802.3 specifications and is useful for enforcing gigabit speeds, as in this case link negotiation is mandatory. If the value is unset (0, the default), the link configuration will be either skipped (if "auto-negotiate" is "no", the default) or will be auto-negotiated (if "auto-negotiate" is "yes") and the local device will advertise all the supported speeds. In Mbit/s, ie 100 == 100Mbit/s. Must be set together with the "duplex" property when non-zero. Before specifying a speed value be sure your device supports it.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.wake-on-lan"></a>wake-on-lan</td>
<td align="left">uint32</td>
<td align="left">1</td>
<td>The NMSettingWiredWakeOnLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2), NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4), NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8), NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST (0x10), NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20), NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40) or the special values NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-3-ethernet.wake-on-lan-password"></a>wake-on-lan-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If specified, the password used with magic-packet-based Wake-on-LAN, represented as an Ethernet MAC address.  If NULL, no password will be required.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.46"></a><h3>wireguard setting</h3>
<p>WireGuard Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.wireguard.fwmark"></a>fwmark</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The use of fwmark is optional and is by default off. Setting it to 0 disables it. Otherwise it is a 32-bit fwmark for outgoing packets. Note that "ip4-auto-default-route" or "ip6-auto-default-route" enabled, implies to automatically choose a fwmark.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wireguard.ip4-auto-default-route"></a>ip4-auto-default-route</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>Whether to enable special handling of the IPv4 default route. If enabled, the IPv4 default route will be placed to a dedicated routing-table and two policy routing rules will be added. The fwmark number is also used as routing-table for the default-route, and if fwmark is zero, a unused fwmark/table is chosen automatically. This corresponds to what wg-quick does with Table=auto. Leaving this at the default will enable this option automatically if ipv4.never-default is not set and there are any peers that use a default-route as allowed-ips.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wireguard.ip6-auto-default-route"></a>ip6-auto-default-route</td>
<td align="left">NMTernary (int32)</td>
<td align="left"> </td>
<td>Like ip4-auto-default-route, but for the IPv6 default route.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wireguard.listen-port"></a>listen-port</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>The listen-port. If listen-port is not specified, the port will be chosen randomly when the interface comes up.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wireguard.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple fragments. If zero a default MTU is used. Note that contrary to wg-quick's MTU setting, this does not take into account the current routes at the time of activation.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wireguard.peer-routes"></a>peer-routes</td>
<td align="left">boolean</td>
<td align="left">TRUE</td>
<td>Whether to automatically add routes for the AllowedIPs ranges of the peers. If TRUE (the default), NetworkManager will automatically add routes in the routing tables according to ipv4.route-table and ipv6.route-table. If FALSE, no such routes are added automatically. In this case, the user may want to configure static routes in ipv4.routes and ipv6.routes, respectively.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wireguard.peers"></a>peers</td>
<td align="left">array of 'a{sv}'</td>
<td align="left"> </td>
<td>Array of dictionaries for the WireGuard peers.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wireguard.private-key"></a>private-key</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The 256 bit private-key in base64 encoding.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wireguard.private-key-flags"></a>private-key-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "private-key" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.47"></a><h3>802-11-wireless setting</h3>
<p>Wi-Fi Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.assigned-mac-address"></a>assigned-mac-address</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The new field for the cloned MAC address. It can be either a hardware address in ASCII representation, or one of the special values "preserve", "permanent", "random" or "stable". This field replaces the deprecated "cloned-mac-address" on D-Bus, which can only contain explicit hardware addresses. Note that this property only exists in D-Bus API. libnm and nmcli continue to call this property "cloned-mac-address".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.band"></a>band</td>
<td align="left">string</td>
<td align="left"> </td>
<td>802.11 frequency band of the network.  One of "a" for 5GHz 802.11a or "bg" for 2.4GHz 802.11.  This will lock associations to the Wi-Fi network to the specific band, i.e. if "a" is specified, the device will not associate with the same network in the 2.4GHz band even if the network's settings are compatible.  This setting depends on specific driver capability and may not work with all drivers.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.bssid"></a>bssid</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, directs the device to only associate with the given access point.  This capability is highly driver dependent and not supported by all devices.  Note: this property does not control the BSSID used when creating an Ad-Hoc network and is unlikely to in the future.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.channel"></a>channel</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Wireless channel to use for the Wi-Fi connection.  The device will only join (or create for Ad-Hoc networks) a Wi-Fi network on the specified channel.  Because channel numbers overlap between bands, this property also requires the "band" property to be set.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.cloned-mac-address"></a>cloned-mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>This D-Bus field is deprecated in favor of "assigned-mac-address" which is more flexible and allows specifying special variants like "random". For libnm and nmcli, this field is called "cloned-mac-address".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.generate-mac-address-mask"></a>generate-mac-address-mask</td>
<td align="left">string</td>
<td align="left"> </td>
<td>With "cloned-mac-address" setting "random" or "stable", by default all bits of the MAC address are scrambled and a locally-administered, unicast MAC address is created. This property allows to specify that certain bits are fixed. Note that the least significant bit of the first MAC address will always be unset to create a unicast MAC address. If the property is NULL, it is eligible to be overwritten by a default connection setting. If the value is still NULL or an empty string, the default is to create a locally-administered, unicast MAC address. If the value contains one MAC address, this address is used as mask. The set bits of the mask are to be filled with the current MAC address of the device, while the unset bits are subject to randomization. Setting "FE:FF:FF:00:00:00" means to preserve the OUI of the current MAC address and only randomize the lower 3 bytes using the "random" or "stable" algorithm. If the value contains one additional MAC address after the mask, this address is used instead of the current MAC address to fill the bits that shall not be randomized. For example, a value of "FE:FF:FF:00:00:00 68:F7:28:00:00:00" will set the OUI of the MAC address to 68:F7:28, while the lower bits are randomized. A value of "02:00:00:00:00:00 00:00:00:00:00:00" will create a fully scrambled globally-administered, burned-in MAC address. If the value contains more than one additional MAC addresses, one of them is chosen randomly. For example, "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00" will create a fully scrambled MAC address, randomly locally or globally administered.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.hidden"></a>hidden</td>
<td align="left">boolean</td>
<td align="left">FALSE</td>
<td>If TRUE, indicates that the network is a non-broadcasting network that hides its SSID. This works both in infrastructure and AP mode. In infrastructure mode, various workarounds are used for a more reliable discovery of hidden networks, such as probe-scanning the SSID.  However, these workarounds expose inherent insecurities with hidden SSID networks, and thus hidden SSID networks should be used with caution. In AP mode, the created network does not broadcast its SSID. Note that marking the network as hidden may be a privacy issue for you (in infrastructure mode) or client stations (in AP mode), as the explicit probe-scans are distinctly recognizable on the air.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.mac-address"></a>mac-address</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>If specified, this connection will only apply to the Wi-Fi device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.mac-address-blacklist"></a>mac-address-blacklist</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of permanent MAC addresses of Wi-Fi devices to which this connection should never apply.  Each MAC address should be given in the standard hex-digits-and-colons notation (eg "00:11:22:33:44:55").</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.mac-address-randomization"></a>mac-address-randomization</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>One of NM_SETTING_MAC_RANDOMIZATION_DEFAULT (0) (never randomize unless the user has set a global default to randomize and the supplicant supports randomization),  NM_SETTING_MAC_RANDOMIZATION_NEVER (1) (never randomize the MAC address), or NM_SETTING_MAC_RANDOMIZATION_ALWAYS (2) (always randomize the MAC address). This property is deprecated for 'cloned-mac-address'. Deprecated: 1</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.mode"></a>mode</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Wi-Fi network mode; one of "infrastructure", "mesh", "adhoc" or "ap".  If blank, infrastructure is assumed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.mtu"></a>mtu</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.powersave"></a>powersave</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>One of NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2) (disable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_ENABLE (3) (enable Wi-Fi power saving), NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1) (don't touch currently configure setting) or NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0) (use the globally configured value). All other values are reserved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.rate"></a>rate</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, directs the device to only use the specified bitrate for communication with the access point.  Units are in Kb/s, ie 5500 = 5.5 Mbit/s.  This property is highly driver dependent and not all devices support setting a static bitrate.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.security"></a>security</td>
<td align="left">None</td>
<td align="left"> </td>
<td>This property is deprecated, but can be set to the value '802-11-wireless-security' when a wireless security setting is also present in the connection dictionary, for compatibility with very old NetworkManager daemons.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.seen-bssids"></a>seen-bssids</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of BSSIDs (each BSSID formatted as a MAC address like "00:11:22:33:44:55") that have been detected as part of the Wi-Fi network.  NetworkManager internally tracks previously seen BSSIDs. The property is only meant for reading and reflects the BSSID list of NetworkManager. The changes you make to this property will not be preserved.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.ssid"></a>ssid</td>
<td align="left">byte array</td>
<td align="left"> </td>
<td>SSID of the Wi-Fi network. Must be specified.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.tx-power"></a>tx-power</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>If non-zero, directs the device to use the specified transmit power. Units are dBm.  This property is highly driver dependent and not all devices support setting a static transmit power.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless.wake-on-wlan"></a>wake-on-wlan</td>
<td align="left">uint32</td>
<td align="left">1</td>
<td>The NMSettingWirelessWakeOnWLan options to enable. Not all devices support all options. May be any combination of NM_SETTING_WIRELESS_WAKE_ON_WLAN_ANY (0x2), NM_SETTING_WIRELESS_WAKE_ON_WLAN_DISCONNECT (0x4), NM_SETTING_WIRELESS_WAKE_ON_WLAN_MAGIC (0x8), NM_SETTING_WIRELESS_WAKE_ON_WLAN_GTK_REKEY_FAILURE (0x10), NM_SETTING_WIRELESS_WAKE_ON_WLAN_EAP_IDENTITY_REQUEST (0x20), NM_SETTING_WIRELESS_WAKE_ON_WLAN_4WAY_HANDSHAKE (0x40), NM_SETTING_WIRELESS_WAKE_ON_WLAN_RFKILL_RELEASE (0x80), NM_SETTING_WIRELESS_WAKE_ON_WLAN_TCP (0x100) or the special values NM_SETTING_WIRELESS_WAKE_ON_WLAN_DEFAULT (0x1) (to use global settings) and NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE (0x8000) (to disable management of Wake-on-LAN in NetworkManager).</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.48"></a><h3>802-11-wireless-security setting</h3>
<p>Wi-Fi Security Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.auth-alg"></a>auth-alg</td>
<td align="left">string</td>
<td align="left"> </td>
<td>When WEP is used (ie, key-mgmt = "none" or "ieee8021x") indicate the 802.11 authentication algorithm required by the AP here.  One of "open" for Open System, "shared" for Shared Key, or "leap" for Cisco LEAP.  When using Cisco LEAP (ie, key-mgmt = "ieee8021x" and auth-alg = "leap") the "leap-username" and "leap-password" properties must be specified.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.fils"></a>fils</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Indicates whether Fast Initial Link Setup (802.11ai) must be enabled for the connection.  One of NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_FILS_DISABLE (1) (disable FILS), NM_SETTING_WIRELESS_SECURITY_FILS_OPTIONAL (2) (enable FILS if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_FILS_REQUIRED (3) (enable FILS and fail if not supported).  When set to NM_SETTING_WIRELESS_SECURITY_FILS_DEFAULT (0) and no global default is set, FILS will be optionally enabled.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.group"></a>group</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of group/broadcast encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list.  For maximum compatibility leave this property empty.  Each list element may be one of "wep40", "wep104", "tkip", or "ccmp".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.key-mgmt"></a>key-mgmt</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Key management used for the connection.  One of "none" (WEP), "ieee8021x" (Dynamic WEP), "wpa-psk" (infrastructure WPA-PSK), "sae" (SAE) or "wpa-eap" (WPA-Enterprise).  This property must be set for any Wi-Fi connection that uses security.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.leap-password"></a>leap-password</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The login password for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.leap-password-flags"></a>leap-password-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "leap-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.leap-username"></a>leap-username</td>
<td align="left">string</td>
<td align="left"> </td>
<td>The login username for legacy LEAP connections (ie, key-mgmt = "ieee8021x" and auth-alg = "leap").</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.pairwise"></a>pairwise</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>A list of pairwise encryption algorithms which prevents connections to Wi-Fi networks that do not utilize one of the algorithms in the list. For maximum compatibility leave this property empty.  Each list element may be one of "tkip" or "ccmp".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.pmf"></a>pmf</td>
<td align="left">int32</td>
<td align="left">0</td>
<td>Indicates whether Protected Management Frames (802.11w) must be enabled for the connection.  One of NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) (use global default value), NM_SETTING_WIRELESS_SECURITY_PMF_DISABLE (1) (disable PMF), NM_SETTING_WIRELESS_SECURITY_PMF_OPTIONAL (2) (enable PMF if the supplicant and the access point support it) or NM_SETTING_WIRELESS_SECURITY_PMF_REQUIRED (3) (enable PMF and fail if not supported).  When set to NM_SETTING_WIRELESS_SECURITY_PMF_DEFAULT (0) and no global default is set, PMF will be optionally enabled.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.proto"></a>proto</td>
<td align="left">array of string</td>
<td align="left"> </td>
<td>List of strings specifying the allowed WPA protocol versions to use. Each element may be one "wpa" (allow WPA) or "rsn" (allow WPA2/RSN).  If not specified, both WPA and RSN connections are allowed.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.psk"></a>psk</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII passphrase of 8 to 63 characters that is (as specified in the 802.11i standard) hashed to derive the actual key, or the key in form of 64 hexadecimal character. The WPA3-Personal networks use a passphrase of any length for SAE authentication.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.psk-flags"></a>psk-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "psk" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.wep-key-flags"></a>wep-key-flags</td>
<td align="left">NMSettingSecretFlags (uint32)</td>
<td align="left"> </td>
<td>Flags indicating how to handle the "wep-key0", "wep-key1", "wep-key2", and "wep-key3" properties. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.wep-key-type"></a>wep-key-type</td>
<td align="left">NMWepKeyType (uint32)</td>
<td align="left"> </td>
<td>Controls the interpretation of WEP keys.  Allowed values are NM_WEP_KEY_TYPE_KEY (1), in which case the key is either a 10- or 26-character hexadecimal string, or a 5- or 13-character ASCII password; or NM_WEP_KEY_TYPE_PASSPHRASE (2), in which case the passphrase is provided as a string and will be hashed using the de-facto MD5 method to derive the actual WEP key.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.wep-key0"></a>wep-key0</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Index 0 WEP key.  This is the WEP key used in most networks.  See the "wep-key-type" property for a description of how this key is interpreted.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.wep-key1"></a>wep-key1</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Index 1 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.wep-key2"></a>wep-key2</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Index 2 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.wep-key3"></a>wep-key3</td>
<td align="left">string</td>
<td align="left"> </td>
<td>Index 3 WEP key.  This WEP index is not used by most networks.  See the "wep-key-type" property for a description of how this key is interpreted.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.wep-tx-keyidx"></a>wep-tx-keyidx</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>When static WEP is used (ie, key-mgmt = "none") and a non-default WEP key index is used by the AP, put that WEP key index here.  Valid values are 0 (default key) through 3.  Note that some consumer access points (like the Linksys WRT54G) number the keys 1 - 4.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.802-11-wireless-security.wps-method"></a>wps-method</td>
<td align="left">uint32</td>
<td align="left">0</td>
<td>Flags indicating which mode of WPS is to be used if any. There's little point in changing the default setting as NetworkManager will automatically determine whether it's feasible to start WPS enrollment from the Access Point capabilities. WPS can be disabled by setting this property to a value of 1.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="id-1.2.7.4.49"></a><h3>wpan setting</h3>
<p>IEEE 802.15.4 (WPAN) MAC Settings.</p>
<div class="informaltable"><table class="informaltable" border="1">
<colgroup>
<col>
<col>
<col>
<col>
</colgroup>
<thead><tr>
<th>Key Name</th>
<th>Value Type</th>
<th>Default Value</th>
<th>Value Description</th>
</tr></thead>
<tbody>
<tr>
<td align="left">
<a name="nm-settings.property.wpan.channel"></a>channel</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>IEEE 802.15.4 channel. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wpan.mac-address"></a>mac-address</td>
<td align="left">string</td>
<td align="left"> </td>
<td>If specified, this connection will only apply to the IEEE 802.15.4 (WPAN) MAC layer device whose permanent MAC address matches.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wpan.page"></a>page</td>
<td align="left">int32</td>
<td align="left">-1</td>
<td>IEEE 802.15.4 channel page. A positive integer or -1, meaning "do not set, use whatever the device is already set to".</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wpan.pan-id"></a>pan-id</td>
<td align="left">uint32</td>
<td align="left">65535</td>
<td>IEEE 802.15.4 Personal Area Network (PAN) identifier.</td>
</tr>
<tr>
<td align="left">
<a name="nm-settings.property.wpan.short-address"></a>short-address</td>
<td align="left">uint32</td>
<td align="left">65535</td>
<td>Short IEEE 802.15.4 address to be used within a restricted environment.</td>
</tr>
</tbody>
</table></div>
</div>
<hr>
<div class="refsect2">
<a name="secrets-flags"></a><h3>Secret flag types:</h3>
<p>
            Each password or secret property in a setting has an associated <span class="emphasis"><em>flags</em></span> property
            that describes how to handle that secret. The <span class="emphasis"><em>flags</em></span> property is a bitfield
            that contains zero or more of the following values logically OR-ed together.
          </p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem"><p>0x0 (none) - the system is responsible for providing and storing this secret. This
              may be required so that secrets are already available before the user logs in.
              It also commonly means that the secret will be stored in plain text on disk, accessible
              to root only. For example via the keyfile settings plugin as described in the "PLUGINS" section
              in <a class="link" href="NetworkManager.conf.html" title="NetworkManager.conf"><span class="citerefentry"><span class="refentrytitle">NetworkManager.conf</span>(5)</span></a>.
              </p></li>
<li class="listitem"><p>0x1 (agent-owned) - a user-session secret agent is responsible for providing and storing
              this secret; when it is required, agents will be asked to provide it.</p></li>
<li class="listitem"><p>0x2 (not-saved) - this secret should not be saved but should be requested from the user
              each time it is required. This flag should be used for One-Time-Pad secrets, PIN codes from hardware tokens,
              or if the user simply does not want to save the secret.</p></li>
<li class="listitem"><p>0x4 (not-required) - in some situations it cannot be automatically determined that a secret
              is required or not. This flag hints that the secret is not required and should not be requested from the user.</p></li>
</ul></div>
</div>
</div>
<div class="refsect1">
<a name="files"></a><h2>Files</h2>
<p><code class="filename">/etc/NetworkManager/system-connections</code> or distro plugin-specific location</p>
</div>
<div class="refsect1">
<a name="see_also"></a><h2>See Also</h2>
<p><a class="link" href="NetworkManager.html" title="NetworkManager"><span class="citerefentry"><span class="refentrytitle">NetworkManager</span>(8)</span></a>,
        <a class="link" href="nmcli.html" title="nmcli"><span class="citerefentry"><span class="refentrytitle">nmcli</span>(1)</span></a>,
        <a class="link" href="nmcli-examples.html" title="nmcli-examples"><span class="citerefentry"><span class="refentrytitle">nmcli-examples</span>(7)</span></a>,
        <a class="link" href="NetworkManager.conf.html" title="NetworkManager.conf"><span class="citerefentry"><span class="refentrytitle">NetworkManager.conf</span>(5)</span></a></p>
</div>
</div>
<div class="footer">
<hr>Generated by GTK-Doc V1.29</div>
</body>
</html>